|
|
|
|
|
Dear Sam-yang, "200806_★NUGU LED UX_Final_0924_English.pdf" is updated. Please find "200806_★NUGU LED UX_0.7ver_English.pptx" which is attached. Thanks KANG, |
|
|
Hi Wooshin, For record, this is the demo videos of beamforming until today. https://drive.google.com/drive/u/1/folders/1Kjg0voE2Sl9kdM9RuOzl0osvnSITBulS I will update videos, and if there is any question, please tell me. THX. |
|
|
Dear Sam-yang, 1. I share video files for sound mute, max, and control. Please check attached files. 2. volume display. ( 32 steps) If you consider two led could display 3 steps using brightness, 20 led can 30 steps. And 1 led can display last 2 steps. Thanks. sound_mute.mov (6,647,724 bytes) sound_max.mov (7,761,995 bytes) sound_control.mov (11,507,010 bytes) |
|
|
Thanks, Wooshin, I will implement according to this. |
|
|
Hi Sam, I think, order of LEDS from left but, it is from right in current s/w. Please check it. |
|
|
There is remained jobs. please check my comment. |
|
|
OK, I'll check with HW and modify it. |
|
|
"I think, order of LEDS from left but, it is from right in current s/w." => fixed at the FW version newer then "v522r07" |
|
|
Hi sam, Please explain current status about status of side led ? thanks. |
|
|
Hi Wooshin, The "HAL_frontpanel.h" has been updated by M/W, and I will report to you when I finish implementation. => sound field LEDs scenarios will be added in the FW version "v522r12". |
|
|
HI sam, I found some differenece between AI2's behavior and attached document. so I have checked it with SKB manager and i got confirmation what they want. They want swan to operate same with AI2. Please check behavior of AI2's LED, we have to make same with AI2. I will check also, how many different is there with document ? Thanks. |
|
|
OK, I'll modify scenario if I find the difference. |
|
|
Hi sam, I can see side led "ON" in current version. but it is not working as specification. Please check attached picture. sound_filed.PNG (77,191 bytes) |
|
|
Hi sam, Please update progress of this ticket. |
|
|
Hi Wooshin, According to M/W definition interface (HAL_frontpanel.h), I only see the scenarios: "Standard", "News", "Music", "Movie": as the picture shows. the HAL_frontpanel.h file need to be added this scenario. Do I misunderstand? hal_frontpanel_h.PNG (27,603 bytes) |
|
|
It is all, You need to implement these 5 options. Thanks |
|
|
OK, I'll implement it. |
|
|
Page 6. "Listening" does not action. Log 12-21 14:19:31.328 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:19:31.328 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 2 : 6 12-21 14:19:31.330 431 610 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 2, state 6 12-21 14:19:31.331 431 610 I FXC_STUB_LP50XX: lp50xx_set_led_state, 1975, unknown command. LED ID 2, state 6 12-21 14:19:31.331 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true 12-21 14:19:31.451 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:19:38.454 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:19:38.455 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 2 : 5 12-21 14:19:38.459 431 610 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 2, state 5 12-21 14:19:38.459 431 610 I FXC_STUB_LP50XX: lp50xx_set_led_state, 1975, unknown command. LED ID 2, state 5 12-21 14:19:38.460 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true 12-21 14:19:38.838 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:19:38.839 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 2 : 5 12-21 14:19:38.841 431 610 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 2, state 5 12-21 14:19:38.841 431 610 I FXC_STUB_LP50XX: lp50xx_set_led_state, 1975, unknown command. LED ID 2, state 5 12-21 14:19:38.841 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true Page 7 "Speaking" does not action Log 12-21 14:28:35.504 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:28:35.505 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 2 : 7 12-21 14:28:35.506 431 431 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 2, state 7 12-21 14:28:35.506 431 431 I FXC_STUB_LP50XX: lp50xx_set_led_state, 1975, unknown command. LED ID 2, state 7 12-21 14:28:35.506 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true 12-21 14:28:36.544 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:28:36.544 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 2 : 9 12-21 14:28:36.545 431 431 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 2, state 9 12-21 14:28:36.545 431 431 I FXC_STUB_LP50XX: lp50xx_set_led_state, 1975, unknown command. LED ID 2, state 9 12-21 14:28:36.545 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true 12-21 14:28:36.788 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 14:28:36.789 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 2 : 9 12-21 14:28:36.790 431 431 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 2, state 9 12-21 14:28:36.790 431 431 I FXC_STUB_LP50XX: lp50xx_set_led_state, 1975, unknown command. LED ID 2, state 9 12-21 14:28:36.791 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true 12-21 14:28:36.792 2700 5254 D NuguStateAction: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON I will check more. |
|
|
Volume control is different action with AI2. Boot animation is different action with AI2. Please check attached movie. volume_animation.mp4 (4,988,979 bytes) boot_animation.mp4 (11,001,996 bytes) |
|
|
Page 8 "BT connection dose not action" LOG 12-21 15:08:39.230 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:08:39.231 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:39.350 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:39.354 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:08:39.445 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:08:39.469 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:46.284 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:08:46.284 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:46.442 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:08:46.443 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:46.488 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:46.488 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:08:50.141 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skb.intent.KEY_LED_BLINK, BUILD_DATE:2020.12.16 12-21 15:08:50.145 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|48|IN| LEDControl: try : setLedState : 3 : 2 12-21 15:08:50.146 17339 17346 I HAL_frontpanel: HAL_FrontPanelSetLedState, 66, in, LED idx 3, state 2 12-21 15:08:50.298 2199 2199 D BtvService0.1.26 PeripheralService: BTF|setLedState|72|OUT| LEDControl: result : setLedState : true 12-21 15:08:56.193 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:08:56.196 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:09:01.504 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:09:01.505 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:09:01.639 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:09:01.641 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:09:01.761 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skbb.intent.action.NUGU_LED_PATTERN, BUILD_DATE:2020.12.16 12-21 15:09:01.761 2700 2700 D TVSIntentReceiver: SKIP LED CONTROL BECAUSE NUGU CALL IS GOING ON 12-21 15:09:02.034 2199 2199 D BtvService0.1.26 IBtvService: BTF|onReceive|66|IN| DeviceCtrlServiceReceiver::onReceive action = com.skb.intent.KEY_LED_BLINK, BUILD_DATE:2020.12.16 |
|
|
page 12, page 13 "Mic" is not action. |
|
|
OK, I'll fix it before 12/28. |
|
|
Hi Sam, Do you have any update on this issue and still the same schedule as 12/28 ? |
|
|
Bug fixes in "v522r28", please verify with this version. |
|
|
When come back from "mute" , volume level is not displayed. <reproduced steps> < Current status > ==> < Expected status > 1. press mute key of rcu, stb mute. ==> ok 2. press mute key again, Led off ==> press mute key again, current volume level should be displayed and after some time, led off Please fix it. |
|
|
I have tuned led scenario with skb manager and i have many issue which should be fixed. Three led documents were integrated into one, and today's tuned content was included. I am translating this and will deliver it to you by tomorrow. Please implement it as soon as possible. And the 2nd tuning is scheduled to be held on January 8th, so I hope that it will be finished before that. |
|
|
Hi, Wooshin I understand and will do my best to fit the schedule. THX. |
|
|
Please check attached file. https://www.dropbox.com/s/0mn6mirkq5eunq1/Motion_Guideline_ver1.1.pptx?dl=0 I am sorry but they want to change several item. Please understand. Thanks. |
|
|
Hi Sam, Please check my comment of 0005645. Thanks, |
|
|
OK, I'll fix it. |
|
|
I had meeting for led with SKB manager. They give me color value. please change color RGB. NUGU LED Blue (140, 165, 225) White (220, 105, 80) Green(120, 255, 115) orange(255, 40, 0) Red(255,0,0) Sound field LED White(220, 205, 110) Yellow(235, 125, 0) cyan(140, 255, 225) orange(255.60.0) pink(255, 58, 120) And Sound field led transition change like : old color -(0.7s)-> black -(0.4s)-> new color. Thanks, |
|
|
Hi Sam, I will have third meeting for led at tomorrow with SKB manager. Please apply color rgb value of 5828. Thanks. |
|
|
Below official document after second tunning. Please refer revision history (page 3) to check what is changed. https://www.dropbox.com/s/7fj7ucydb0048gi/Motion_Guideline_ver1.2.pptx?dl=0 Thanks. |
|
|
Hi, Wooshin I have applied color rgb value of 5828, you can use the next released FW. |
|
|
Hi, Wooshin specifications of 5828 and 5848 are conflict, which one I should follow? |
|
|
Please follow 5848 |
|
|
As I talked with Wooshin, we will compare scenarios with AI2 and modify parameters, then verified by ALT pals, then we discuss what need to be modified. |
|
|
hi, Wooshin As we talked, I'll prepare dynamically-tuning tool for you this Friday morning. And after this days tuning, I have pushed commits of "Volume Change", "Volume Mute", "Listen Start", "Listen Active", "Process", "Speaking", please verify. Thanks. Comparing videos with AI2: Listen Start: https://drive.google.com/file/d/1Nx2tsKZI77YPK6IK83h0dTn8vAbUJsYn/view?usp=sharing Speaking: https://drive.google.com/file/d/19ChRC6NsVlxRlIyiIodVlcSc6fdacstG/view?usp=sharing Volume Change: https://drive.google.com/file/d/1FQSMLvDNphAoNXnz9NbD8EGZt_c2M8vk/view?usp=sharing Volume Mute: https://drive.google.com/file/d/1-E3bWadT29XPooB5TmR6Eydj2Qb8hgp1/view?usp=sharing |
|
|
Hi, Wooshin I already push commits for dynamically tuning. The way is by using configuration files. 1.Please use the newest code base FW (*** userdebug build ***) after 2021/1/21/21:05. 2.After the device booting, type console commands below: (every reboot should "setenforce 0") su setenforce 0 mkdir /data/led_frontpanel_config echo "700000 400000 5000 220 205 110 255 220 205 110" > /data/led_frontpanel_config/led_sound_field_leds.txt echo "255 255 255 255 1000000" > /data/led_frontpanel_config/led_status_led.txt echo "140 165 225 400000 1 5000 255 4.5 1.0 0.0 3.5 300000" > /data/led_frontpanel_config/led_state_listen_wakeup.txt echo "140 165 225 1000000 5 5000 255 4.5 1.0 0.0 3.5 300000" > /data/led_frontpanel_config/led_state_listen_active.txt echo "140 165 225 1000000 1 5000 255 1.5 1.5 0.0 3.5 300000" > /data/led_frontpanel_config/led_state_listen_end.txt echo "140 165 225 600000 1 5000 255 1.5 3.5 0.0 3.5 300000" > /data/led_frontpanel_config/led_state_listen_process.txt echo "130000 20000 1 1000 1000 255 255 255 255 16 2.5 15.0 2.5 4.0 2.3 0.3" > /data/led_frontpanel_config/led_state_volume.txt echo "140 255 255 5 350000 30000 350000 1000 100000 255 3.0 16.2" > /data/led_frontpanel_config/led_state_speaking_speaking.txt echo "140 165 225 3 50000 240000 50000 1000 0 255 3.8 13.0" > /data/led_frontpanel_config/led_state_bt_on.txt echo "140 165 225 3 50000 240000 50000 1000 0 255 3.8 13.0" > /data/led_frontpanel_config/led_state_bt_off.txt echo "255 40 0 3 50000 240000 50000 1000 0 255 3.8 13.0" > /data/led_frontpanel_config/led_state_mic_on.txt echo "255 40 0 3 50000 240000 50000 1000 0 255" > /data/led_frontpanel_config/led_state_mic_off_when_call.txt echo "255 0 0 3 50000 240000 50000 1000 0 255 3.8 13.0" > /data/led_frontpanel_config/led_state_system_error.txt echo "3 1000 255 2.5 5000000 2500000 16 2500000 0 700000 300000 0.0" > /data/led_frontpanel_config/led_state_sys_boot.txt echo "220 105 80 3 1000 255 0 350000 3.5 8.0" > /data/led_frontpanel_config/led_state_call_ringtone.txt echo "220 105 80 1 1000 255 0 200000 5.0 10.0" > /data/led_frontpanel_config/led_state_call_start.txt echo "220 105 80 3 1000 255 0 800000 3.5 13.0" > /data/led_frontpanel_config/led_state_call_calling.txt echo "220 105 80 1 1000 255 0 200000 5.0 10.0" > /data/led_frontpanel_config/led_state_call_end.txt chmod 666 /data/led_frontpanel_config/led_sound_field_leds.txt chmod 666 /data/led_frontpanel_config/led_status_led.txt chmod 666 /data/led_frontpanel_config/led_state_listen_wakeup.txt chmod 666 /data/led_frontpanel_config/led_state_listen_active.txt chmod 666 /data/led_frontpanel_config/led_state_listen_end.txt chmod 666 /data/led_frontpanel_config/led_state_listen_process.txt chmod 666 /data/led_frontpanel_config/led_state_volume.txt chmod 666 /data/led_frontpanel_config/led_state_speaking_speaking.txt chmod 666 /data/led_frontpanel_config/led_state_bt_on.txt chmod 666 /data/led_frontpanel_config/led_state_bt_off.txt chmod 666 /data/led_frontpanel_config/led_state_mic_on.txt chmod 666 /data/led_frontpanel_config/led_state_mic_off_when_call.txt chmod 666 /data/led_frontpanel_config/led_state_system_error.txt chmod 666 /data/led_frontpanel_config/led_state_sys_boot.txt chmod 666 /data/led_frontpanel_config/led_state_call_ringtone.txt chmod 666 /data/led_frontpanel_config/led_state_call_start.txt chmod 666 /data/led_frontpanel_config/led_state_call_calling.txt chmod 666 /data/led_frontpanel_config/led_state_call_end.txt 3.notice that every reboot should "setenforce 0". |
|
|
Every parameter meaning are here: https://docs.google.com/document/d/1Ho5wER9OqFQ6aTJJnxQGuYzUjTdAALApl2X26OOeCcI/edit?usp=sharing I know there are many many parameters, so I already tune some scenarios these days, and I'll do it tomorrow(Friday), but because we don't know which scenarios SKB manager will want to tune, I think the best way is you try all once. If there is any problem, let me know. Thanks～ |
|
|
I am saying repeat that SKB wants it is same with AI2, anyway i will checking it tomorrow. i will be back. Thanks |
|
|
I know, so I'm trying to make the same as AI2 these days, and I tuned the scenario "Speak" that you said too slow then AI2. Please use the config file and verify, thanks. And please feedback config files contents if there is any change. |
|
|
for history, https://docs.google.com/document/d/1Ho5wER9OqFQ6aTJJnxQGuYzUjTdAALApl2X26OOeCcI/edit# |
|
|
hi, Wooshin Modification of new parameters and SKB Motion Guideline v1.4 has been pushed to git remote on 01/26. Please verify it, thank you. |
|
|
Hi Sam, I will update my test result on next monday. |
|
|
|
|
|
record the newest specification: |
|
|
Hi Sam, TEST Version : 19.522.44 ( It is released in dawn of 2/10), http://altserver01.iptime.org/release_by_fxn/swan_nightly/ I have 2 issue by simple test. 1. BT connection scenario is ok, BT disconnection is not OK ( no action ) 2. Tuning value is not applied. Please check it. |
|
|
Hi Wooshin, about these two issues: 1.Jim will fix this. 2.Please type "setenforce 0" to console and try again. thanks. |
|
|
Hi Sam, 2 .Please type "setenforce 0" to console and try again. Even though i change it, result is same. no led_frontpanel_config. Thanks. |
|
|
led_frontpanel_config.PNG (142,100 bytes) |
|
|
Hi, Wooshin As WeChat discussion, I have added the config folder led_frontpanel_config built-in. Please use the FW after 20210223 12:39 code base to verify. And find the console commands from "ReadMe_LedDynamicallyTuning" txt file: su setenforce 0 echo "100000 50000 5000 220 205 110 255 220 205 110" > /data/vendor/led_frontpanel_config/led_sound_field_leds.txt ...... |
|
|
Hi, Wooshin Issue "LED scenario Speak too slow" is fixed. Please verify it with the FW of code base after 2021/02/26 17:00. Thanks. |
|
|
Hi, Wooshin Issue "LED scenario Speak sometimes don't show out" is fixed. Please verify it with the FW of code base after 2021/03/05 20:00. Thanks. |
|
|
Hi Sam, I will monitor and update if any issue is founded. Thanks. |
|
|
Hi sam, Please check implementation on page 22 of "Motion_Guideline_ver1.4_20210125.pptx" when user press mic button on front ( on -> off ), orange coler led pattern should be displayed 3 times but no action. Thanks. |
|
|
Hi sam, The led should indicate all states even if the state changes rapidly. For example, 1. if state change (1->2->3) in 10 millisecond, you should display 1 and 2 and 3. 2. if you get change state during previous motion, new motion should be started when previous motion is finished. Do not interrupt previous motion. Thanks. |
|
|
Any update..? |
|
|
Hi, Wooshin I was dealing with DVT stuff last week, and will report where if there's any update of LEDs. |
|
|
Hi, Wooshin "when user press mic button on front ( on -> off ), orange coler led pattern should be displayed 3 times" => already fixed, please verify with the FW of after-2021/04/19-19:00 code base. Thanks~ |
|
|
Hi sam, "The led should indicate all states even if the state changes rapidly" When will be fixed it..? |
|
|
HI sam, About mic button (on->off and off->on), i had misunderstand. Please change like below. ON->OFF : 1 time motion. OFF->ON : 3 times motion. I am sorry again. Thanks. |
|
|
Hi, Wooshin 1."The led should indicate all states even if the state changes rapidly" => I need to modify for new AMP boards for DVT3 manufacturing, so this will be fixed after DVT3. 2.About mic button (on->off and off->on) => I'll change it next week. |
|
|
It is reported by SKB QA. |
|
|
Any update..? |
|
|
Please update about current status. |
|
|
Hi Wooshin , 1."The led should indicate all states even if the state changes rapidly" => I need to discuss with Sam. I have a question. If the state is motion state , how do we show it ? 2.About mic button (on->off and off->on) => i already commit , you can check in next firmware release. Jerry |
|
|
HI jerry, I need to discuss with Sam. I have a question. If the state is motion state , how do we show it ? -> Actually i don't know exact concept, i think that checking behavior of AI2 box is best. And this requirement is also made form observation of AI2 behavior. And we have no enough time to implement it. It should be finished before BMT (5/4). Thanks. |
|
|
Any update..? |
|
|
Hi Wooshin, I have discussed with sam about led motion, the led structure is currently being modified, and the results of the changes need to be tested. This may take time. It is expected to take until May 4. Jerry |
|
|
HI jerry, Is it applied at bitbucket ? Please update about current status. Thanks. |
|
|
Hi Wooshin, I sync with Sam about the current status again. There will be a version available on the evening of MAY 7th. We suggest to check the verified version on early Monday morning. If it can be completed in advance, I will let you know immediately. Jerry |
|
|
Hi all, I am sorry but i am very angry. Behavior of LED is getting worse and worse. It looks commit source code without test. It is difficult to explain what is wrong behavior due to everything is strange. Please fix it urgently. Thanks, |
|
|
Hi Wooshin , We had commit led tuning and beamforming issue , Please check in new firmware (commit date is 0513). Jerry |
|
|
Hi jerry, Thanks for your effort but we have to do 5th tune woks with SKB manager because they want. I will be started at 15: 00 5th May. Thanks. |
|
|
Target date is 2th June for source code commit of 5th tune. |
- yk.jung ( (ALTech) Younkwang Jung ) developer
